New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
!!!FEATURE: Add virtual object configurations for framework loggers #2134
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved by reading - format is as we discussed in original PR
I'm not a good writer at all. But I'm a believer of iterative incremental improvement.
Added some docs for the logging part of Flow that was still missing. It's very basic still, but any help is highly welcome! |
Q: Is a code migration possible that replaces
and
with the above? i.e. multi-line replacements? |
TODO:
|
That will be a great addition to the docs 🤩 |
cc @lorenzulrich - maybe you have something to add/improve? I'm really bad at (technical) writing in a way that it is user-friendly/understandable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one, thanks for pushing this topic!
Co-authored-by: Bastian Waidelich <b.waidelich@wwwision.de>
Also replaced nearly all of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, apart from that logger change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I don't see an improvement for the case of the system logger, despite of having "configuration over convention" (🤔). But as long as the LoggerInterface still defaults SystemLogger implementation, I don't want to block this.
Personally I don't see an improvement for the case of the system logger, despite of having "configuration over convention" (🤔). But as long as the LoggerInterface still defaults SystemLogger implementation, I don't want to block this.
Yeah, it's not an "improvement" for that case. But this is more about making the injection of any logger straight forward through a single documented method. More about consistency than anything else. |
Co-authored-by: Bastian Waidelich <b.waidelich@wwwision.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good (by reading)
Thanks a lot for taking care!
I reverted the removal of the Edit: Missed a few places where the logger can be injected via annotation safely. |
With this, it is possible to inject the Flow
systemLogger
,securityLogger
,sqlLogger
andi18nLogger
via the virtual objectsNeos.Flow:SystemLogger
,Neos.Flow:SecurityLogger
,Neos.Flow:SqlLogger
andNeos.Flow:I18nLogger
respectively.Note: This also removes the deprecated
PsrSecurityLoggerInterface
andPsrSystemLoggerInterface
, which should be replaced by injections like above.Resolves #2125